method and system for performing remote diagnostics in a vehicle

专利摘要:
METHOD AND SYSTEM FOR PERFORMING REMOTE DIAGNOSIS IN A VEHICLE. A method and system for performing software diagnostics or maintenance on a vehicle is described which comprises recording high fidelity data on the vehicle consistent with configuration files to support engineering analysis or diagnostics with vehicle components, systems or performance (S220). Supplemental data is retrieved through an in-vehicle low-bandwidth transmission to supplement the recorded high-fidelity data (S222). The recorded high-fidelity data and retrieved supplementary data are processed to generate a transmission diagnostic status report message to the central electronic data processing system organizes the diagnostic report message, the recorded high-fidelity data and the data. supplements retrieved from a market data or diagnostic database to support engineering analysis or diagnostics on components, systems, or vehicle performance (S226).
公开号:BR112013003141B1
申请号:R112013003141-7
申请日:2011-08-24
公开日:2021-05-25
发明作者:Michael R. Johnson；Daniel Colavita；Tammy R. Pullen
申请人:Deere & Company；
IPC主号:

专利说明:

Field of Invention
[001] This invention relates to a method and system for performing diagnostics or software maintenance for a vehicle. Fundamentals of the Invention
[002] In certain prior art, remote diagnosis and analysis of vehicle performance may require storage and transmission of complete configuration files from a central processing unit to vehicle electronics. Such transmission tends to inefficiently use one or more communication channels between the central processing unit and the vehicle's electronic components. A land-based communication channel may be unavailable or unreliable where the vehicle and associated vehicle electronics are located in rural areas, such that a satellite communication channel is required. For example, transmission of complete configuration files, and hence remote diagnostics, may not be economically viable, where more expensive satellite communication channels are required to handle significant data output in complete configuration files.
[003] In some prior art, remote diagnosis and analysis of vehicle performance may require different software payloads to accommodate both local in-vehicle connection through a short-range wired or wireless connection, and remote in-vehicle connection through a wireless communication system. Distinct software payloads tend to require duplicative software that can tax the software's processing power or the data processing output of the vehicle's electronic components. For example, software updates or diagnostics processed by vehicle electronics may run slower because of duplicative software, or other software in vehicle electronics may perform slowly where less data processing capabilities are available.
[004] In certain prior art, diagnostic capabilities may be limited to the baud rate capability of a vehicle data bus, such as a controller area network (CAN) data bus. In this way, engine control events that occur at rates greater than the vehicle's data bus baud rate can be ignored in certain prior art diagnostic systems, which can lead to less accurate and more accurate diagnostic procedures. time-consuming.
[005] Thus, there is a need to increase the efficiency and performance of a method to perform remote diagnosis of a vehicle to address the aforementioned problems. Invention Summary
[006] According to an embodiment, a method and system for performing software diagnostics or maintenance on a vehicle comprises recording high-fidelity data on the vehicle consistent with configuration files to support engineering analysis or diagnostics on components, systems or performance of vehicle. Supplemental data is retrieved through an in-vehicle low-bandwidth transmission to supplement the recorded high-fidelity data. The recorded high fidelity data and retrieved supplementary data are processed to generate a transmission diagnostic status report message to the central electronic data processing system. A data processor or central electronic data processing system organizes the diagnostic report message, the recorded high-fidelity data, and the retrieved supplementary data into a data marketplace or diagnostic database to support engineering analysis or diagnostics of the data. components, systems or vehicle performance. Brief Description of Drawings
[007] FIG. 1 is a block diagram of a system for performing diagnostics or software maintenance of vehicle electronic components in accordance with the invention.
[008] FIG. 2A is a flowchart of an embodiment of a method for performing software diagnostics or maintenance of vehicle electronics.
[009] FIG. 2B is a flowchart of another embodiment of a method for performing software diagnostics or maintenance of vehicle electronics.
[0010] FIG. 2C is a flowchart of yet another modality of a method for performing software diagnostics or maintenance of vehicle electronics.
[0011] FIG. 3 is a block diagram of system software modules and components for performing software diagnostics or maintenance, consistent with FIG. 1.
[0012] FIG. 4 is a flowchart of a process to retrieve machine configuration workflow.
[0013] FIG. 5 is a flowchart of a process for managing data logging requests to facilitate diagnosis or evaluation of vehicle performance or vehicle electronics.
[0014] FIG. 6 is a flowchart of a process for managing a user's selected language.
[0015] FIG. 7 is a flowchart of a process for reprogramming vehicle electronics.
[0016] FIG. 8A is a process flowchart for processing errors after applying a task, payload, or update to vehicle electronics.
[0017] FIG. 8B is a process flowchart for detecting and managing corruption messages or tasks.
[0018] FIG. 9 is a flowchart of a process for importing engineering configurations for vehicle or vehicle electronics into the central data processing system.
[0019] FIG. 10 is a block diagram of the billing system for performing software diagnostics and maintenance for a vehicle. Description of the Preferred Mod
[0020] According to an embodiment, FIG. 1 illustrates a remote diagnostic system 11. In one embodiment, the remote diagnostic system 11 comprises a central electronic data processing system 10 that is capable of communicating with vehicle electronics 46 via a communication network 36 and wireless infrastructure. wire 44.
[0021] The central electronic data processing system 10 and wireless infrastructure 44 are coupled to an electronic communication network 36 (e.g., the Internet). One or more service technician terminals (e.g., first service technician terminal 40 and a second service technician terminal 42) are capable of communicating with the central electronic data processing system 10 via communication network 36. One or more service technician terminals (40, 42) are capable of communicating with vehicle electronics 46 via communication network 36 and wireless infrastructure 44.
[0022] In an alternative embodiment, a service technician or user may use a local diagnostic computer 38 that communicates directly with the vehicle electronics 46 via a short-range wireless connection, a wired connection, or another local connection. For example, the service technician can use the local diagnostic computer 38 to communicate with the vehicle electronics 46 if a vehicle is located at a service center, or is brought to it, where the service technician works. Otherwise, the service technician can remotely perform some of the many diagnostic and software programming tasks via the communication network 36 and the wireless infrastructure 44.
[0023] The central electronic data processing system 10 comprises a remote data processor 12, a remote data storage device 14, and a remote communication interface 18 coupled to a data bus 16. In one embodiment, the system The central electronic data processing system 10 can be implemented by a general purpose computer or a server which is programmed with modules stored in software in the remote data storage device 14. The remote data processor 12 is capable of communicating with one or more of the following over the data bus 16: the remote data storage device 14 and remote communication interface 18. The remote data storage device 14 stores one or more of the following software modules, structures or data files: a generator of payload 22, a configuration file generator 23, a recalibrator 20, a common message interface, a billing manager 32, files configuration 30 (eg components of configuration files 30), an analyzer 26 and a diagnostic database 28 (eg data market).
[0024] The remote data processor 12 may comprise a microprocessor, a microcontroller, a central processing unit, a programmable logic arrangement, an application-specific integrated circuit (ASIC), a logic circuit, an arithmetic logic unit, or another data processing system 10 for processing, storing, retrieving or manipulating electronic data.
[0025] Remote data storage device 14 comprises electronic memory, non-volatile random access memory, an optical storage device, a magnetic storage device, or another device for storing and accessing electronic data on any electronic storage media , optical or magnetic recordable, rewritable, or readable.
[0026] The remote communication interface 18 may comprise a transceiver or other device for communicating, transmitting or receiving data over the communication network 36. In one embodiment, the communication network 36 comprises the Internet, the public switched telephone network ( PSTN) or another public or private electronic communication network 36, or a communications link (eg, telecommunications line or microwave link) that supports bidirectional communication with the wireless infrastructure 44.
[0027] The payload generator 22 comprises a software module or instructions for organizing, assembling or generating payloads or configuration file components for programming or reprogramming one or more of the following devices: the vehicle electronics 46, a controller 73, or an engine controller 74. The payload generator 22 can read configuration files 30 or components of configuration files that are as installed in the vehicle electronics 46 for a particular vehicle with a vehicle identifier or a machine identifier. The payload generator 22 can also read target settings for a vehicle identifier or a corresponding machine identifier, where the target settings are stored in remote data storage device 14 or are accessible by the central electronic data processing system 10. Target settings are typically established by the vehicle manufacturer or the supplier of various electronic modules for the vehicle.
[0028] The recalibrator 20 comprises a software module or instructions for organizing, assembling or generating calibration data to program, reprogram or establish the state or parameter value of one or more of the following devices: the vehicle electronics 46, a controller 73, or a motor controller 74. The recalibrator 20 can read configuration files 30, component configuration files, or calibration data that represent calibration data in the installed form (e.g., factory or manufacturer settings for parameters) in the vehicle electronics 46 for a particular vehicle with a vehicle identifier or a machine identifier. The recalibrator 20 can also read target calibrations to a vehicle identifier or a corresponding machine identifier, where the target calibrations are stored in remote data storage device 14 or are accessible by the central electronic data processing system 10. The target calibrations may be established by the vehicle manufacturer, a supplier of various electronic modules for the vehicle, or a service technician or engineer in such a way that the vehicle meets certain performance standards, emission standards, fuel economy targets, or other goals consistent with customer satisfaction and regulatory requirements. The recalibrator 20 is capable of performing automatic recalibration of components of vehicle electronics 46 that are outside a target range of parameter values. Recalibrator 20 may perform such automatic recalibration in response to the results of a diagnostic report message provided by data processing system 10 or analyzer 26.
[0029] The configuration file generator 23 comprises a software module or instructions for generating, managing, archiving, storing and retrieving configuration data for corresponding vehicles with respective vehicle identifiers. Configuration data can be pertinent to components from configuration files to unload payloads or provision for vehicle electronics. The configuration file can store configuration files 30 or components of configuration files that can be organized or rearranged due to the modular format of the components of the configuration files.
[0030] An analyzer 26 comprises a software module or instructions for analyzing diagnostic test results, fault codes, error messages, status messages, or test results provided by the vehicle electronics 46 to the data processing system. central electronic data 10 through wireless infrastructure 44 and communication network 36.
[0031] A diagnostic database 28 comprises a database or other collection of records or data files that can be used to store diagnostic history of corresponding vehicles or vehicles with respective vehicle identifiers. Additionally, the diagnostic database 28 may contain market reference vehicle models or market reference vehicle performance models that provide market reference values of measurements of the vehicle electronics 46 to facilitate the identification of abnormal operating conditions , for example.
[0032] In one embodiment, the billing manager 32 may include at least a portion of the billing system 911 of FIG. 10. Billing manager 32 comprises a software module or instructions to facilitate billing for the provision of diagnostics, remote programming, local programming, or other technical support of vehicle electronics 46 and associated controllers (73, 74).
[0033] The first service technician terminal 40 and the second service technician terminal 42 each comprise a computer. The first service technician terminal 40 and the second service technician terminal 42 each comprise a user interface 41. A user interface 41 may comprise a numeric keypad, an alphanumeric keyboard, a pointing device (e.g., mouse electronic), a monitor, or other device for feeding or outputting data from the first service technician terminal 40, the second service technician terminal 42, or another computer.
[0034] Wireless infrastructure 44 supports wireless communications between vehicle electronics 46 and one or more of the following devices: a first service technician terminal 40, a second service technician terminal 42, and a processing system electronic data center 10. Wireless infrastructure 44 may comprise one or more of the following: one or more wireless base stations that are capable of communicating over communication network 36 through a port with an Internet service provider, or other way; one or more satellite transceivers; a satellite downlink receiver, a satellite uplink transmitter; a satellite communication system; a cellular infrastructure network; a trunk system, a point-to-multipoint communication system, a point-to-point communications link, a wireless ground-based communication network 36, or the like.
[0035] Vehicle electronic components 46 comprise a vehicle data processor 71, a vehicle data storage device 56, and a vehicle wireless communication device 58, a data port 48, a user interface 54 , a vehicle data bus (e.g., controller area network (CAN) data bus) 72, a controller 73, and an engine controller 74. The data processor 71 is capable of communicating with one or more of the following devices via a data bus 16: vehicle data storage device 56, data port 48, user interface 54, and vehicle wireless communication device 58.
[0036] Data port 48 provides an interface such as common memory between a data bus 50 and a vehicle data bus 72. A controller 73 and an engine controller 74 are coupled to the vehicle data bus 72. Controller 73 and engine controller 74 may have electronic memory (e.g., non-volatile random access memory) or another storage device for storing, retrieving and processing payload data, calibration data, configuration data, loads. useful components of configuration files or other computer instructions that are downloaded or provided via the local diagnostic computer 38 or via the electronic data processing system 10.
[0037] Vehicle data storage device 56 stores or contains one or more of the following software modules, data structures, or archives a register 60, a retriever 62, an unloader 64, and a manager 66. A register 60 comprises a software module or instructions for recording data collected by controller 73, engine controller 74, a sensor, an actuator, a network device coupled to the vehicle data bus 72, or capable of communicating with it, or another sensor or measuring device for sending or measuring parameters, conditions or state of vehicle electronics 46, vehicle systems, or vehicle components. A downloader 64 comprises a software module or instructions that facilitate downloading, monitoring the download, and communicating with one or more of the following: payload, configuration data, parameter settings, calibration data, configuration file components, modules software, or similar. A manager 66 comprises a software module or instructions that facilitate installation, monitoring, management and reversing or reversing one or more of the following: payload, configuration data, parameter settings, calibration data, configuration file components, software modules, or similar. A retriever 62 comprises a software module or instructions for responding to status queries regarding status (eg installation status) or software module versions, payloads, configuration data, calibration data, file components. configuration, technical specifications, processor configuration, input/output configuration, operating system software, hardware adjustments, hardware architecture, or other information related to one or more controllers (73, 74), vehicle electronics 46, or software installed on each.
[0038] The vehicle data processor 71 may comprise a microprocessor, a microcontroller, a central processing unit, a programmable logic arrangement, an application-specific integrated circuit, a logic circuit, an arithmetic logic unit, or another system of data processing to process, store, retrieve or manipulate electronic data.
[0039] Vehicle data storage device 56 comprises electronic memory, non-volatile random access memory, an optical storage device, a magnetic storage device, or another device for storing and accessing electronic data on any storage media recordable, rewritable, or readable electronic, optical or magnetic.
[0040] A user interface 54 comprises one or more of the following: a numeric keypad, an alphanumeric keyboard, a touch screen display, a key, a pointing device (e.g., electronic mouse), a monitor (by example, liquid crystal display or plasma display), or another device for feeding, entering, selecting, receiving, or displaying input or output data to a computer, controller, electronic components, or other electronic data processing system.
[0041] Data port 48 may comprise an input/output data port 48, such as a UART, a data transceiver with buffer memory, a device that supports communications with the local diagnostic computer 38, or a interface device that supports communication between the data bus 50 and the vehicle data bus 72.
[0042] In an alternative embodiment, data port 48 may comprise a short-range wireless connection, such as an IEEE (Institute of Electrical and Electronics Engineers) 802.11 connection or a bluetooth wireless connection. Data port 48 supports a connection, transmission, reception or exchange of data between the vehicle electronics 46 and the local diagnostic computer 38.
[0043] In another alternative embodiment, the remote data storage device 14 or the vehicle data storage device 56 comprises or stores a common message interface for communication with vehicle electronic components 46, the common message interface providing a communication interface between vehicle electronics 46 and at least one application program.
[0044] In FIG. 1, the vehicle electronics 46 further comprise a resource monitor 74, an alert timer 72, reset logic 73, a corruption task module 65, and a cycle counter 75. In one embodiment, the resource monitor 74, alert timer 72, reset logic 73, corruption task module 65, and cycle counter 75 can be used for detecting and managing a corruption message, corrupt task, or problematic software code. which can consume excessive computational resources or cause the data processor 71 to become involved in a repetitive cycle, which causes the data processor 71 to stop operating the software or certain software instructions, or which contributes to another process unwanted. As illustrated in FIG. 1, resource monitor 74, alert timer 72, and reset logic 73 can communicate with data processor 71 or corruption task module 75 (or cycle counter 75) in the data storage device. of the vehicle 56 via the data bus 50. Additionally, the alert timer 72 and the reset logic 73 can communicate with each other via the data bus 50, or directly via a transmission line or an electrical conductor (not shown).
[0045] Resource monitor 74 comprises an electronic device or software instructions for monitoring resource level consumption, processing output, processing duration, or processing capacity of data processor 71, for a corresponding task performed or to is performed by data processor 71. For example, resource monitor 74 may comprise a detector for detecting a request by data processor 71, or received by it, to perform a particular task, an executable file, executable software instructions or instruction sets and a timer for measuring the duration for data processing or completion by the data processor 71 of a corresponding task, an executable file or other software instructions or executable instruction sets. A task refers to any discrete, identifiable process, procedure or series of processes and procedures that are applied to input data, output data, intermediate data derived from the input data, or a precursor to the output data by the data processor. data 71. For example, a task may include trigger-based recording of the performance of a controller 73 or a motor controller 74, or diagnostic data associated therewith.
[0046] The alert timer 72 comprises a timer and a control circuit, an electronic device, or software instructions that control the maximum possible duration of time for each task or process to be performed by the data processor. In one embodiment, the alert timer 72 has a maximum possible duration of time set or set by the technician that can be adjusted based on the particular operating system and application software (e.g., maximum expected duration for a data processor to run a cycle of the software, a particular task or group of tasks) to be performed by the data processor 71. The alert timer 72 may be triggered by the software (eg application software or a particular task in the application software) where there is a infinite loop or an infinite loop at interrupt level (eg in application software or a particular task), for example. When the data processor 71 (e.g., microprocessor), the software or task executable by it, and the necessary hardware supporting the data processor 71 is operating normally or at sufficient speed, the alert timer 72 ordinarily prevents the processor 71 is reset or reset by clearing a trigger signal or trigger value in a data log (prior to the expiration of an alert interruption period). However, when the data processor 71, the software or task executable by it, or the required hardware supporting the data processor 71 is not operating normally or with sufficient speed, the alert timer 72 cannot clear or reset the signal. trigger or trigger value in the data log, which, upon expiration of the alert interruption period, triggers the reset logic 73 to reset or reset the data processor 71. For example, the alert timer 72 may be unable to clear the trigger signal or trigger value in the data register if the data processor 71 is stuck in a cycle, delays the execution of a task or interrupts the execution of a task during execution of the task or executable file. Although alert timer 72 and reset logic 73 are illustrated as separate blocks in FIG. 1, alert timer 72 and reset logic 73 can be integrated into a data processor 71.
[0047] The reset logic 73 comprises a logic circuit, a controller or software instructions for providing a digital signal, a logic level signal or other reset signal to the data processor 71 to reset or reset the data processor 71 The reset logic 73 can be configured to send the reset signal via data bus 50 to data processor 71, or directly to a reset data input (not shown) of data processor 71, which may vary by device. data processor to data processing device.
[0048] As illustrated in FIG. 1, the vehicle storage device 56 further comprises a corruption task module 65 and a cycle counter 75. The corruption task module 65 comprises program instructions for detecting one or more corruption tasks, program instructions for managing one or more corruption tasks, program instructions for segregating one or more corruption tasks for non-execution, and program instructions for deleting one or more corruption tasks.
[0049] A 75 cycle counter comprises software instructions or an electronic counter for storing, accessing, retrieving, writing or reading data in one or more data storage registers or other data storage locations to track the number of times that a cycle was executed for a particular task corresponding to an executable program. As illustrated in FIG. 1, the cycle counter 75 is stored in the corruption task module 65, accessible or managed by it. The cycle counter 75 is stored in such a way that turning off the vehicle electronics 46 or resetting or resetting the data processor 71 does not interrupt or interfere with the ability to read or access data that was previously stored in the cycle counter 75.
[0050] FIG. 2A is a flowchart of one modality of a method for performing software diagnostics or maintenance on a vehicle. The method of FIG. 2A starts at step S200.
[0051] At step S200, a central electronic data processing system 10 stores one or more configuration file components 30 for access by the central electronic data processing system 10. For example, the configuration file components 30 are arranged as a modular set of files that support electronic communication between the central electronic data processing system 10 and vehicle electronics 46, or between a local diagnostic computer 38 and vehicle electronics 46. The configuration files or components can be configured as payloads or configuration data that are suitable for remote transfer between the central data processing system 10 and the vehicle electronics 46 (for example, or the controllers 73, 74), for example. Configuration data comprises instructions, patches, components or software modules that are based on vehicle configurations and vehicle electronics 46. In general, configuration data is functionally and operationally compatible with the engine controller 74 and the controller 73 for the particular vehicle, which may depend on the operating system compatibility of the software or source code in the controllers (73, 74) or the type (eg manufacturer) of data processors (eg microprocessors) used in the controllers (73 , 74).
[0052] At step S202, the central electronic data processing system 10 or a service technician terminal (40, 42) requests an update of the stored configuration files 30 for the vehicle electronics 46, in a particular vehicle, of the central electronic data processing system 10, or by it. The requested update can be based on a user request (eg via a terminal 40, 42), or automatically generated by the central electronic data processing system 10 as part of a software modernization cycle, after the lapse of a period of time, for a call from the product manufacturer to correct any faults related to the vehicle, or upon the occurrence of another trigger event that is defined by a user or manufacturer of the vehicle.
[0053] At step S204, the vehicle electronics 46 receive the requested update as components of configuration files 30 from the central electronic data processing system 10 based on a comparison of a record of the configuration files installed on the vehicle 30 and target configuration information in configuration files 30 stored in the central electronic data processing system 10 (or in the data storage device). For example, the vehicle electronics 46 receive the requested components from the configuration files through a wireless infrastructure and communication network, where the wireless infrastructure comprises a land-based wireless system, a satellite communication system, or both. The ground-based wireless system may be used, except where it does not provide reliable coverage or a signal of adequate signal quality to the vehicle electronics 46 or the vehicle's wireless communication device 58. Satellite is used as an auxiliary communication system for the land-based wireless system when or if the land-based system does not provide reliable coverage or a signal of adequate signal quality to the vehicle's wireless communication device. .
[0054] In one embodiment, the configuration files installed on the vehicle 30 comprise an as-loaded list of software that is loaded onto the vehicle electronics 46 (or associated controllers) in accordance with archived records of the central electronic data processing system 10. Prior to receiving components of the configuration files in the vehicle electronics 46, the data processing system 10 can check whether the configuration files installed in the vehicle are current or up to date by sending a status inquiry message from the system software central data processing for the vehicle electronics 46, or controllers (73, 74) associated with or residing therein. The target configuration information in the configuration files 30 comprises a target list of software for loading into the vehicle, where the target list is associated with a corresponding valid time period. If the valid time period expires, the data processing system 10 can be programmed to update or check the status or accuracy of the software target list by contacting (for example, via communication network 36) a manufacturer of the vehicle or components vehicle electronics, or data records provided on behalf of the manufacturer of the vehicle or vehicle electronic components.
[0055] Alternatively, configuration file records installed in vehicle 30 and corresponding target configuration for each vehicle may be stored in one or more central databases that are accessible by the central electronic data processing system 10 through a network of electronic communication 36, a local communication network 36 (eg Ethernet) or otherwise.
[0056] After updating the configuration or software in the vehicle electronics 46 (for example, in step S204), the vehicle electronics 46 generate a feedback or confirmation file for transmission of the vehicle electronics 46 to the processing system data center 10 via wireless infrastructure 44 and communication network 36. The return file may contain a user identifier or hardware identifier that initiated the reprogramming or requested the update (eg payload, component, data configuration file or configuration file). Additionally, the return file may contain information regarding the Media Access Control (MAC) address or host identifier of a computer (e.g., first service technician terminal 40 or second service technician terminal 42) that started reprogramming (eg of components). The MAC address represents a unique identifier for computer hardware that is assigned by a hardware manufacturer.
[0057] For a remote programming environment, a controller not programmed in the vehicle electronics 46 may generate a fault code when it cannot communicate with another controller (for example, a controller being reprogrammed) temporarily during the process reprogramming. For example, vehicle electronics 46 can be instructed to automatically reset the above-referenced fault code, or the (vehicle) operator can be provided with instructions to reset or clear such program fault codes manually.
[0058] The software configuration in installed form or in-vehicle installed configuration of a vehicle may be updated from time to time by one or more transmissions of vehicle electronic components 46 to the data processing system 10. For example, after the vehicle electronics 46 of a vehicle are updated by installing or downloading a software payload, the vehicle electronics 46 can generate a confirmation or status update of current software that has been successfully installed on the electronics of the vehicle 46.
[0059] FIG. 2B refers to another embodiment of a method for performing remote software diagnostics or maintenance on a vehicle. The method of FIG. 2B starts at step S230.
[0060] At step S230, a central data processing system 10 or a remote data storage device 14 stores software components for vehicle electronic components 46 in a central electronic data processing system 10 or in a database accessible by electronic data processing system 10.
[0061] In step S232, the central data processing system 10 determines whether an update of the software loaded in the vehicle electronics 46 is either unsolicited or required. The update is requested if it is requested by a user or technician who has had permission from the vehicle owner to perform diagnostics, repair the vehicle, or update or service software on the vehicle. The update is required if the update is required to comply with the vehicle manufacturer's warranty, a call from the product manufacturer to correct any faults associated with the vehicle or vehicle electronics 46, a vehicle upgrade, or other instructions provided by the vehicle manufacturer. If update is required or requested, the method continues with step S236. However, if the update is neither requested nor required, the method continues with step S234.
[0062] In step S234, the central data processing system 10 waits a time interval before returning to step S232.
[0063] At step S236, the central data processing system 10 or a terminal (e.g., first service technician terminal 40 or a second service technician terminal 42) requests an update of the software loaded in the vehicle electronics 46 from the central electronic data processing system 10. For example, a service technician may request an update of the loaded software while still performing routine maintenance or service on the vehicle associated with the vehicle electronics 46.
[0064] At step S238, the central data processing system 10 generates a common payload or patch, compatible with the remote and local connection in the vehicle electronics 46 and consistent with the requested update. For example, the central data processing system 10 generates a payload in response to a request for software update in vehicle electronics 46, or in one or more controllers (73, 74). In one embodiment, common payload processing software dynamically assembles payloads that are machine-specific and customized, as opposed to reprogramming an entire group of vehicles of the same model number with the same software payload. To establish and assemble the appropriate dynamically mounted payload for the vehicle, the electronic data processing system 10 considers: (a) the difference between a software record as loaded (eg, stored or managed by the data processing system central 10) and the target software configuration and (b) the optional vehicle configuration (eg factory options selected by the original purchaser). For example, options can affect the engine's torque curve, transmission configuration, or other features.
[0065] A payload can comprise configuration data, calibration data, or both. Configuration data refers to a particular configuration of vehicle electronics 46, a controller, a vehicle system, or a vehicle in which one or more vehicle features are active, inactive, or set to match selected vehicle options (by eg factory vehicle options ordered on the original vehicle). Calibration data can refer to parameter settings that can be adjusted to meet various requirements or engineering operating standards. Calibration data can refer to parameters that are adjusted for fuel consumption, fuel economy, torque requirements, engine emission standards, pollution control targets (eg NOx (nitrous oxide reduction), power requirements engine, hydraulic system performance, electrical system power or current output, environmental conditions (eg, ambient temperature, humidity, terrain elevation), or meeting other vehicle specifications. Payload data, configuration data, and calibration data is associated with a corresponding vehicle identifier for storage, retrieval or indexing on the remote data storage device 14.
[0066] In step S240, the vehicle electronics 46 receive the common payload or patch generated by the central electronic data processing system 10. For example, one or more controllers (73, 74) within the vehicle electronics 46 can be reprogrammed with the common payload or patch from the central electronic data processing system 10. Vehicle electronics 46 or controllers (73, 74) can be reprogrammed to a state where the software in the installed form matches a configuration target for software in vehicle electronics 46, or where the performance of vehicle electronics 46 or vehicle meets a vehicle specification. Calibration data, configuration data, or both can be established or optimized for particular environmental conditions, authorized vehicle resources, or otherwise.
[0067] In step S242, the central data processing system 10 or the vehicle electronics 46, or both, can install the common payload or patch generated in the vehicle electronics 46. Step S242 can be performed according to various techniques that can be applied separately or cumulatively.
[0068] According to a first technique, the central data processing system 10 uses common payload processing software (eg 350 in FIG. 3) in the central data processing system 10, a local diagnostic computer 38, or both, where the same payload can be remotely distributed through remote programming of vehicle electronics 46 (via communications with vehicle wireless communication device 58) via a communication network 36 and wireless infrastructure 44 and locally by local programming via a short-range wired or wireless connection between a vehicle electronics data port and the local diagnostic computer 38.
[0069] According to a second technique, the central data processing system 10 uses common payload processing software (eg 350 in FIG. 3) to install or reprogram a payload, configuration data, configuration data. calibration, or configuration software components for an engine controller 74 and a non-engine controller (eg 73) simultaneously simultaneously. Here, simultaneously simultaneous must mean in general simultaneously, occurring at the same time plus or minus three seconds, occurring alternately such as time division multiplexed, or occurring alternately during alternating time windows of equal or different duration.
[0070] According to a third technique, the central data processing system 10 uses common payload processing software (eg 350) to reprogram or install a payload, configuration data, calibration data, or components of configuration software on a first controller (eg 73 or 74) that is working properly and ignore a second controller (eg 73 or 74) other than the first controller that is malfunctioning or not responding to one or more data messages, or that it is generating an error code or diagnostic code.
[0071] According to a fourth technique, the central data processing system 10 facilitates displaying a common payload programming status or a patch to a user through a user interface 54 of the vehicle electronics 46 or a user interface 41 of a first service technician terminal 40 or a second service technician terminal 42.
[0072] According to a fifth technique, the central data processing system 10 facilitates allowing a user to control the progress of programming the vehicle with the common payload or patch through a user interface 54 of the vehicle electronics 46 or a user interface 41 of a first service technician terminal 40 or a second service technician terminal 42.
[0073] According to a sixth technique, the central data processing system 10 can install the generated common payload in a manner that allows the central data processing system 10 to revert the vehicle electronics 46 to a programming state. above, upon a request generated by a technician or user of a first service technician terminal 40, second service technician terminal 42, user interface 54 of vehicle electronics 46, or otherwise. For example, the central data processing system 10 can store past payload data, past configuration data, past calibration data, current payload data, current configuration data, and current calibration data in a file, a archive, an inverted file, a data record, a database or other suitable data structure. In this way, the vehicle electronics 46, the data processing system 10, or the service technician (e.g., from a terminal 40, 42) can return to the current configuration data, current payload, or calibration data. 46 current vehicle electronics or vehicle electronics for a previous setup or calibration, available from previously stored setup data, previous calibration data, and previous payload data.
[0074] In one example, the vehicle electronics 46, the central data processing system 10, or the user (for example, via a local diagnostic computer 38 or the user interface 54 of the vehicle electronics 46 ) can trigger current payload lap, current configuration, or current calibration data before payload, before setup, or before calibration data. For example, if the vehicle comprises a combine or a combine, the vehicle electronics 46 in a previous configuration and previous calibration can be optimized for a first crop (e.g., corn), whereas the vehicle electronics 46 in a current setting are optimized for a second crop (eg wheat or soybeans). In this way, the operator or vehicle electronics 46 can revert to the previous configuration and previous calibration to match an operator's crop rotation cycle between the first crop and the second crop such that the vehicle electronics 46 are optimized for the particular corresponding crop that is currently in the crop rotation cycle.
[0075] FIG. 2C also refers to another modality of the method for performing remote diagnostics in a vehicle. The method of FIG. 2C starts at step or block S300.
[0076] At step S220, vehicle electronics 46 records high-fidelity data or higher sample rate data on the vehicle consistent with configuration files 30 to support engineering analysis or diagnostics on vehicle components, systems, or performance. High fidelity data can be defined according to various definitions that can be applied alternatively or cumulatively. According to a first definition, the terms high-fidelity data are synonymous with higher sample rate data with a sampling interval that is greater than the total delay on a vehicle data bus 72 (for example, data bus CAN (controller area network)), where the total delay (eg approximately 0.5 microsecond or more) includes the sum of a propagation delay over the maximum length (eg 10 meters) of the vehicle data bus , a controller processing delay, and a controller transceiver delay.
[0077] According to a second definition, high-fidelity data comprises higher sample rate data that is collected at sampling rates higher than normal than those typically used by controllers (eg motor controller 74 or another controller 73) during normal operation of the vehicle (or normal operation of a particular controller). A normal sampling rate means a sampling rate for data that is necessary or required for a controller (eg engine controller 74) to perform and function properly, in addition to performing any diagnostics or data collection features that are not required for the controller to perform and function properly. A sample rate greater than a lower normal or typical sample rate for a measured parameter can support greater accuracy or better identification of a problem with a vehicle, vehicle system, or component.
[0078] High-fidelity data can be collected by an engine controller 74 or another controller (eg 73) that is associated with sensors or measurement devices, where measured events (eg system injection system events). fuel or fuel metering) occur during periods of time that are less than the total delay. The controller (eg 74) may store the collected high-fidelity data in temporary storage memory (eg external or internal to the controller) or on another data storage device (eg 56). The vehicle data bus 72 or controller area network (CAN) data bus may not have sufficient bandwidth or baud rate capacity to transmit the real-time high-fidelity data as it is collected. Instead, the collected high-fidelity data can be stored and aggregated by a controller (eg 74) for further transmission over the vehicle data bus 72 and for subsequent analysis. For example, if vehicle data bus 72 comprises a CAN data bus, the baud rate can range from 1 megabits per second (Mbps) to 10 kilobits per second (Kbps). At a transmission rate of 10 kilobits per second, each symbol or bit can take up to 100 microseconds to transmit from the vehicle data bus 72 (eg CAN data bus) which can limit real-time capabilities where the CAN data is heavily loaded with traffic or activity, for example.
[0079] In step S222, the vehicle electronics 46 retrieve or record supplemental data via a low-bandwidth transmission in the vehicle to supplement the recorded high-fidelity data. Low bandwidth transmission can be defined according to several definitions that can be applied alternatively or cumulatively. According to a first definition, supplemental data is synonymous with the terms lower sample rate data that is collected at a lower sample rate than the higher sample rate of high-fidelity data.
[0080] According to a second definition, the low-bandwidth transmission comprises a wireless transmission between vehicle electronic components 46 and the central electronic data processing system 10, or another remote data processing system, where the maximum bandwidth (or maximum transmission rate) is limited to meet or exceed a certain minimum level of reliability or signal quality, or to comply with a bandwidth limitation provided by a satellite or other service provider without thread.
[0081] According to a third definition, low-bandwidth transmission is at a data transmission rate or maximum data transmission rate offered or provided by a vehicle data bus 72 (e.g. CAN data), where it is understood that the maximum data transmission rate may be limited by loading the vehicle data bus 72 with traffic, multiple controllers, actuators or other network devices. For example, in step S222, vehicle electronics 46 may provide such low-bandwidth data to central electronic data processing system 10 or analyzer 26 after vehicle electronics 46 have reported or transmitted high-bandwidth data. fidelity pertinent to data processing system 10 or analyzer 26. Vehicle electronics 46 may provide real-time low-bandwidth transmission over vehicle data bus 72 from the controller (e.g., 73 or 74 ) to supplement previously collected high-fidelity data.
[0082] At step S224, the data processing system 10 or the analyzer 26 processes the recorded high-fidelity data and retrieved supplementary data to generate a diagnostic status report message for transmission to the first service technician terminal 40 or to the second service technician terminal 42. In an alternative embodiment, to critically state a failure, error, problem, or malfunction, or to prevent a failure (e.g., catastrophic failure) of the vehicle or vehicle electronics 46 , the data processing system 10 or the analyzer 26 processes the recorded high-fidelity data and retrieved supplementary data to generate a diagnostic status report message for transmission to a user interface 54 of the vehicle electronics 46, the first. service technician terminal 40 or the second service technician terminal 42. Additionally, the diagnostic status report q that is transmitted to the vehicle electronics 46 may instruct the vehicle user or operator to take corrective or preventive measures with respect to the vehicle or vehicle electronics 46.
[0083] In step S226, the data processing system 10 or the diagnostic database 28 organizes the diagnostic report message, the recorded high-fidelity data and the retrieved supplementary data into a data market or database 28 to support engineering analysis and diagnostics on vehicle components, systems or performance.
[0084] Step S226 can be performed according to various techniques that can be applied alternatively or cumulatively. According to a first technique, the data processing system 10 or the diagnostic database 28 organizes the diagnostic report message, the recorded high-fidelity data and the retrieved supplementary data to identify trends in the diagnostic database. 28. According to a second technique, the data processing system 10 determines a diagnostic request status or progress and displays the determined status to a user at a user terminal (40, 42) or electronics user interface of vehicle 46 in communication with central electronic data processing system 10. According to a third technique, data processing system 10 displays real-time data readings from a vehicle to a user at a user terminal (40 , 42) or user interface of vehicle electronic components 46 in communication with the central electronic data processing system 10.
[0085] According to a fourth technique, based on the diagnostic report message, the data processing system 10 and the vehicle electronics user interface 46 support customer selection of a service center to remotely perform service on a vehicle via settings selectable via network address. The list of service centers presented to a particular user may be suitable (a) to have the closest geographic location between the service center and a corresponding particular user, or (b) to have experience or practice in resolving one or more issues or technical problems identified by the diagnostic report message to the particular user.
[0086] According to a fifth technique, a billing system charges one or more users based on usage for service sections and remote diagnostic programming that are selected by a user through the vehicle electronics user interface 46 or via a network address accessed by the user through a personal communication device or computer.
[0087] An engine controller 74 or another controller (eg 73) may be equipped with an internal data monitor or another data collector (not shown) for high fidelity data collection. The internal data monitor can comprise an electronic module, a software module, or both. For example, the data collector may comprise a combination of electronic memory and a data processor 71. Similarly, the internal data monitor in the controller (eg 73 or 74) may comprise a combination of electronic memory and a microprocessor, or another data processor associated with the controller. The software module for the data collector or internal data monitor comprises software instructions for reading, recording, storing, retrieving and managing data in one or more registers, addresses or memory locations of electronic memory consistent with register instructions, logging parameters, sampling intervals, logging duration, or other instructions specified or selected by a user.
[0088] In one embodiment, high-fidelity data refers to data that is sampled at a sampling rate that is greater than a real-time transmission rate or real-time data production rate of a data bus. vehicle 72 (for example, controller area network data bus 72). High fidelity data may also be referred to as higher sample rate data, whereas low bandwidth transmission may be referred to as lower sample rate data or vehicle data bus limited data or width limited data of band. For example, high fidelity data can refer to data that is sampled at a sampling rate that is greater than a real-time baud rate that is operating under normal load conditions, a range of typical load conditions, or full load conditions, for a 72-vehicle data bus. In one example, the sampling rate for the high-fidelity data is less than or equal to 50 milliseconds. In another example, the sample rate for high-fidelity data is less than or equal to 5 milliseconds. In yet another example, the sampling rate for high-fidelity data is less than or equal to 2.5 milliseconds.
[0089] High fidelity data can be collected pertinent to one or more of the following parameters: (a) engine speed, (b) valid bus speed request, (c) desired fuel, (d) governor integral term, (e) proportional term of the governor, and (f) type of governor. High-fidelity data can be used to examine or evaluate the performance of one or more of the following components of a vehicle: fuel injection system, fuel metering system, ignition timing, or other aspects of controlling a vehicle with an internal combustion engine, or a terrain fault detection system for an electrically-propelled vehicle, or an inverter or motor controller to control an electric-drive motor for an electrically-propelled vehicle.
[0090] The controller (73, 74) or vehicle electronics 46 may have data storage or electronic memory (eg external random access memory) which may be divided into one or more storage zones. Vehicle electronics 46 may record or monitor one or more parameters at one or more projected sample rates or a standard sample rate. The vehicle electronics 46, the central data processing system 10 or the technician (via a terminal 40, 42) can set or select one or more of the following: (a) the parameters to be recorded, (b) the sampling rates, (c) a trigger trigger to start logging, (d) a stop trigger to stop logging, (e) memory allocation or data storage allocation, and (f) maximum logging duration or maximum size of logged data. According to a modality, one or more parameters can be registered at the same time by one or more controllers (73, 74). The method of FIG. 2C can be performed by performing tests on the vehicle via a remote terminal (40, 42) in communication with at least one of the vehicle electronics 46 and the central electronic data processing system 10.
[0091] FIG. 3 illustrates a possible software configuration supporting the remote diagnostic system 11 of FIG. 1. Like reference numbers in FIG. 1 and in FIG. 3 indicate equal elements.
[0092] The service center computer application 301 and network dashboard 302 are configured to run on the central electronic data processing system 10 and displayed to a user of the first service technician terminal 40 or the second terminal of service technician 42. The service center computer application 301 may comprise those software modules, data structures and files that are stored in the remote data storage device 14. The service center computer application 301 may facilitate a user selection of a service center that is geographically closest to the vehicle or vehicle electronics 46 that requires analysis, diagnosis, repair, software programming, or software reprogramming.
[0093] The 302 network instrument panel provides the status of upgrade requests, payload transfers, or diagnostic tests to a user interface 41 of a first service technician terminal 40 or a second service technician terminal service 42. Network services for dashboard use 309 support provision of status data about payload transfer, reprogramming or other activities to the dashboard network, consistent with the technical limitations and specifications of the 41 user interface for the first service technician terminal 40, the second service technician terminal, or both.
[0094] The central electronic data processing system 10 performs or supports execution of the following software modules, the following network address hosting and management functions, the following data storage and retrieval functions, the following security functions, and authorization, and other electronic data processing functions: the remote management system and database 303, the communications service host 304, the telematic network address 305, the telematic service 306, the machine identification database 307, the machine telematics signature search database 308, the network service for use of the instrument panel 309 (machine database), and the telematics link in the vehicle 310.
[0095] The remote management system and database 303 may comprise the diagnostic database 28 of FIG. 1, for example. Communications service host 304 may be managed or executed by communication interface 18 of FIG. 1, for example.
[0096] Machine identification database 307 may store authorization records for users (e.g., service technician) and corresponding machine or vehicle identifiers that authorize users to repair, reprogram, reconfigure, review, evaluate or diagnose corresponding electronic components of the vehicle 46 or corresponding vehicles. Machine telematics signature search 308 may be related to which technician terminals (e.g., first service technician terminal 40 or a second service technician terminal 42) are granted access for remote diagnostics or remote programming of electronic components of the vehicle 46.
[0097] The 311 machine connection layer and the 312 remote programming payload processor are common 350 payload software components that can be used for both local and remote programming and analysis of vehicle electronics 46. Local programming it is programming and analysis done through the local diagnostic computer 38 which is connected directly to the vehicle electronics 46 or its data port 48 via a wire, cable, or wireless link. Common payload processing software is common or generally the same for the central electronic data processing system 10 and the local diagnostic computer 38. The central electronic data processing system 10 provides payloads or reprogramming remotely via the communication network 36 and wireless infrastructure 44 to vehicle electronics 46. Local diagnostics computer 38 provides payloads and reprogramming directly to vehicle electronics 46 via local connection. Local diagnostic computer 38 can teleport programming from central electronic data processing system 10 over a communication network 36 or otherwise.
[0098] Common payload processing software comprises a 314 motor connection component, a 315 motor loader program, a 313 non-motor connection component, and a 316 non-motor loader program. or payload can be suitable for different types of motor and non-motor controllers (73, 74). Additionally, redundancy of software features such that (1) reprogramming of non-motor controllers (eg 73) and motor controllers (eg 74) can be done simultaneously, and (2) reprogramming a controller Non-motor (eg 73) can still be made, if an engine controller (eg 74) or software reprogramming software produces a fault or error, and cannot be reprogrammed, and (3) reprogramming a Motor controller (eg 74) can still be made, if a non-motor controller (eg 73) or software produces a fault or error, and cannot be reprogrammed.
[0099] In one mode, during reprogramming, all other controller functions other than programming or writing to its memory can be disabled.
[00100] In another illustrative modality, the common payload software can use a variable environment. The variable environment provides an indicator of whether vehicle electronics 46 are operating in a local reprogramming environment or a remote reprogramming environment. Vehicle electronics 46, central data processing system 10, or both determine whether a variable environment is present that indicates a remote programming environment. If the remote programming environment is detected, the central data processing system 10 can suppress certain elements of a script based on the display capabilities of a user interface 41 on the vehicle electronics 46 or filter the displayed content to eliminate content. technical or technical content that is not considered suitable for an end user of a vehicle, unlike a sophisticated technician (for example, either the user interface 41 of the first service technician terminal 40 or the second service technician terminal 43 ).
[00101] In an alternative mode, in the remote programming environment, the writing can be modified to request machine resources such as tire size or other information that can be used to reprogram the machine.
[00102] The electronic components of the vehicle 46 can facilitate execution of mobile communication services 317, a basic software structure 318, remote diagnostics and internal programming 319, telematics connection 310 in the vehicle, local connection 320 in the vehicle, area network controllers controller (CAN) 321 and vehicle controllers 322. CAN 321 controllers are software that allow one or more controllers (73, 74) to interact with other network elements or communicate over the vehicle's data bus (eg, data bus). CAN data), where network elements may comprise one or more controllers, transceivers, actuators, sensors, or other electronic devices. Vehicle controllers 322 may comprise engine controller 74 and controller 73, for example.
[00103] The process of FIG. 4 starts or starts at step or block 401.
[00104] In step 402, the user or technician enters a machine product identifier (for example, a vehicle identifier) at a terminal (for example, a first service technician terminal 40) or another computer device which is capable of physical or wireless communications with the central electronic data processing system 10 via the communication network 36 (e.g., Internet).
[00105] At step 403, through the terminal or computer device, a user or technician creates a request to retrieve machine information (eg configuration data, calibration data, software such as loaded data, target software data , or other data relating to the electronic components of the vehicle 46 or controllers therein) from the central electronic data processing system 10 or a database accessible through the central electronic data processing system 10.
[00106] In step 404, through the terminal or computer device, the user or technician sends the request created to retrieve machine information to the central electronic data processing system 10 (e.g., host computer) through the network of communication 36 (eg Internet).
[00107] In step 405, the central electronic data processing system 10 determines whether or not the user is authorized. For example, the central electronic data processing system 10 can determine if the user is authorized if the user or technician goes through an authentication process, such as inputting an identifier and a corresponding password. If the user is authorized, the method continues with step 406. However, if the user is not authorized (for example according to an authentication process or security measure), the method continues with block 409.
[00108] At step 406, the central data processing system 10 determines whether the particular vehicle or machine, or its associated vehicle electronics 46, has remote capability. Remote capability means that the vehicle electronics 46 support wireless communications between the central electronic data processing system 10 and the vehicle electronics 46 through the communication network 36 and through any other intermediary (e.g., wireless infrastructure 44). If the vehicle or vehicle electronics 46 has remote capability, the method continues with step 408. However, if the vehicle or vehicle electronics 46 does not have remote capability, the method continues with block 407.
[00109] In step 408, the central data processing system 10 completes one or more of the following acts: (a) the central data processing system 10 retrieves a machine configuration or configuration data for the vehicle in accordance with the product identifier number of the fed machine and the request information, (b) the central data processing system 10 retrieves the machine request information, (c) the central data processing system 10 builds a configuration file dynamically optimized based on machine configuration and user requested information.
[00110] At step 409, the central data processing system 10 returns and displays machine information retrieval results.
[00111] FIG. 5 is a flowchart of a process for a process of logging data from data to vehicle electronics 46. The method of FIG. 5 starts at step or block 501.
[00112] At block 502, a central electronic data processing system 10 retrieves a machine configuration for a user or technician (for example, at a first service technician terminal 40, a second service technician terminal 42, or another terminal capable of communicating with the central electronic data processing system 10 via the communication network 36, or otherwise).
[00113] At block 503, a user (via a terminal user interface 41) activates, enters or selects a data logging feature (eg, a data logging button), toggles, or controls. The user interface 41 may feature the data logging feature in the service center computer application 301, or otherwise.
[00114] At block 504, the central data processing system 10 or the terminal displays a data logging assistant. The data logging assistant comprises a magic, menu-activated instruction set, or other software-assisted mechanism for logging parameters of vehicle electronics 46, or one or more vehicle electronics controllers 46.
[00115] At block 505, the central data processing system 10 selects or enters one or more of the following: record type, record parameters, record conditions, record duration, record trigger event, start time logging, logging stop time, or other user-defined element related to logging.
[00116] At block 506, the central data processing system 10 or the service center computer application 301 creates registration request using information returned from retrieved machine information and the information that the user selected or fed into the assistant. register in block 504, block 505, or both.
[00117] In block 507, the central data processing system 10 generates the dynamic configuration file based on the requested data or registration request.
[00118] At block 508, the service center computer application 301 sends a request to the server (e.g. central data processing system 10). The server or central data processing system 10 forwards or transmits the requested data or registration request to the vehicle electronics 46 for processing. Vehicle electronics 46 may process the request via a controller, an engine controller, or a register 60 in conjunction with a data processor.
[00119] At block 509, the central data processing system 10 or the server validates the request and posts a request on the instrument panel.
[00120] At block 510, sending/receiving results in the workflow. Vehicle electronics 46 collect data in a data logger, recorder 60, controller, or an engine controller. The collected data is grouped according to the registration parameters and registration conditions selected in block 505. Once the collected data is complete according to the request, the electronics of the vehicle 46 transmit or send the workflow of the results (e.g., recorded data or collected data) to central electronic data processing system 10 for analysis by an analyzer 26, storing in a diagnostic database 28, or other appropriate measurements.
[00121] In block 511, the process of FIG. 5 ends.
[00122] FIG. 6 is a flowchart of a process for managing workflow of requests and results. The method of FIG. 6 starts at block 602.
[00123] At block 601, the central data processing system 10 queues a request for delivery to a machine. For example, central data processing system 10 may receive the request from a first service technician terminal 40, a second service technician terminal 42, and another terminal.
[00124] At block 602, the central data processing system 10 determines whether a received request is valid or not. The request received can be validated by an authentication process in which one or more of the following is verified: (a) user identifier and corresponding user password, (b) vehicle identifier and authorization of a particular user associated with the vehicle identifier. user to modify or receive information regarding the vehicle configuration of a corresponding vehicle, (c) request format is not in proper syntax, and (d) requested information is available for the particular vehicle with the feature set or vehicle configuration corresponding. If a request is valid, the method continues with step 604. However, if the request is not valid, the method continues with step 603.
[00125] At block 603, the central data processing system 10 returns an error (eg error message) to the service center computer application 301 and displays the error or error message to a user via a user terminal or a user interface 41. The error message may explain or be related to the statement why the received request was not valid. The error message may explain one or more of the following: (a) user identifier or user password is incorrect, (b) private user associated with user identifier is not authorized to modify or receive information regarding vehicle configuration of a corresponding vehicle, (c) request format is not in proper syntax, and (d) requested information is not available for the particular vehicle with the corresponding set of features or vehicle configuration.
[00126] In block 605, the first service technician terminal 40, the second service technician terminal 42, or a service center computer application 301 therein communicates (e.g., search) to the central data processing system 10 (eg server) at a user-defined frequency or interval to check the results.
[00127] At block 604, the central data processing system 10 (e.g., server) updates or refreshes the screen or user interface status 41 of the first service technician terminal 40, of the second service technician terminal 42 , or from the service center computer application 301 with the 302 network dashboard with a requested state.
[00128] At block 606, the central data processing system 10 (e.g., server) sends the results to the first service technician terminal 40, the second service technician terminal 42, or the service center computer application. service 301, and the results are stored in the remote data storage device 14 or in the remote machine database associated with the central data processing system 10.
[00129] At block 607, the central data processing system 10, the first service technician terminal 40, the second service technician terminal 42, or all of the aforementioned system elements determines whether or not the results have been received or have been received. If results have been received, the method continues with step 608 and step 610.
[00130] However, if the results have not been received, the method continues with step 609.
[00131] At step 608, the central data processing system 10, the first service technician terminal 40, the second service technician terminal 42, or any combination of the aforementioned network elements, converts results to the user language selected for display through a user interface 41.
[00132] In step 610, the user interface 41 of the first technician terminal, the second service technician terminal 42, or the local diagnostic computer 38 displays the results.
[00133] In step 611, the process ends.
[00134] The process of FIG. 7 refers to updating configuration data or other vehicle software data after successful installation of software on vehicle electronics 46. The method of FIG. 7 starts at block 701.
[00135] At block 702, through a user interface 41 of the first service technician terminal 40 or the second service technician terminal 42, the user or service technician selects a vehicle or vehicles to reprogram in the network address of software payload. The software payload network address may be provided or hosted on the central electronic data processing system 10.
[00136] At block 703, via a user interface 41 of the first service technician terminal 40 or the second service technician terminal 42, the user selects a particular controller associated with or within vehicle electronics 46 to reprogram.
[00137] At block 704, via a user interface 41 of the first service technician terminal 40 or the second service technician terminal 42, the user selects or makes an entry in the user interface 41 to send the reprogramming request .
[00138] In block 705, the central data processing system 10 generates the reprogramming payload(s), if the user is authorized to reprogram a respective vehicle with the electronic components of the vehicle 46 and controller particular. Payloads are generated as previously described in this document. The same payloads can be used whether the electronics of the vehicle 46 or controller are locally or remotely programmed.
[00139] At block 706, the central data processing system 10 queues the payload(s) for delivery to the machine(s) or to the vehicle electronics 46. The processing system data center 10 is capable of sending one or more payloads that are queued in its data storage device through communication network 36 and wireless infrastructure 44 to the vehicle electronics
[00140] At block 707, the data processing system 10 updates the network instrument panel 302 that is displayable to the first service technician terminal 40, the second service technician terminal 42, or both. The network instrument panel 302 may be displayed on the terminal user interface 41 to provide a current status of downloading or installing one or more payloads on the vehicle electronics 46 or on a particular vehicle electronics controller 46.
[00141] In block 708, machine interaction occurs, where one or more payloads are transmitted from the data processing system 10 or its data storage device through the communication network 36 and wireless infrastructure 44 to the electronic components of the vehicle 46.
[00142] At block 708, the data processing system 10 waits for the results (e.g., feedback or confirmation file) to be received from the electronics of the vehicle 46 or particular controller that has been reprogrammed or which attempts to be reprogrammed. The results, return or confirmation file provide an indication of whether or not the reprogramming was successful, or other associated indicators (eg, fault codes, diagnostic codes, or diagnostic messages) of the state of the vehicle electronics 46 or of a particular controller.
[00143] In block 710, the central data processing system 10 determines whether the reprogramming was performed without triggering an exceeded interrupt. If the reschedule outage is exceeded, a support mailbox or support case is notified. However, if the reprogramming interrupt is not exceeded, the method continues with step 712.
[00144] In step 712, the central data processing system 10 determines whether the results have been received. If results have been received, the method continues with step 713. However, if results have not been received, the method continues with step 709.
[00145] In step 713, the central data processing system 10 determines whether or not the rescheduling was successful. The data processing system 10 can read the results, feedback file or confirmation transmitted by the vehicle electronics 46 through the wireless infrastructure 44 and the communication network 36 to the central data processing system 10. The data processing system data 10 intercepts or reads the results, return file or confirmation to determine whether or not the reprogramming was successful. If the reprogramming was successful, the method continues with step 714. However, if the reprogramming was not successful, the method continues with step 711. The method ends at step 715 after step 711 or 714.
[00146] The process of FIG. 8A relates to software error processing and updating in vehicle electronics 46. The process of FIG. 8A starts at step 801.
[00147] In step 801, a central data processing system 10 receives a task start request from a first service technician terminal 40 or a second service technician terminal 42.
[00148] At step 802, the central data processing system 10 creates a task based on the start task request if the user is authorized to run the task for a particular machine, vehicle or electronic components of the associated vehicle 46.
[00149] At step 803, a central data processing system 10 checks to determine whether task or task request refers to a corruption message. For example, the central data processing system 10 checks a previous operation or task and previous abnormal reset of a device, or the data processing system 10.
[00150] At step 804, the central data processing system 10 saves the task to a data storage device, such as a magnetic disk, an optical disk, a disk drive, or electronic memory (e.g. non-volatile random access).
[00151] In step 805, the central data processing system 10 schedules the task to execute.
[00152] At block 806, the central data processing system 10 creates a connection on the vehicle data bus 16 (for example, controller area network (CAN) data bus 16).
[00153] Block 807 can be executed simultaneously with block 806, or after or before block 806. In block 807, the central data processing system 10 creates a connection to a vehicle monitor or user interface 41 in the components vehicle electronics 46. The connection may comprise a packet-based communications or communication channel established between data processing system 10 and vehicle electronics 46 via communication network 36 and wireless infrastructure 44.
[00154] At block 808, the central data processing system 10, vehicle electronics 46, or both run the task.
[00155] At block 809, the central data processing system 10 and the vehicle electronics 46 send a status update to the vehicle monitor or user interface 41.
[00156] At block 811, the central data processing system 10, the vehicle electronics 46, or both determine whether the task has been completed successfully. If the task has completed, the method continues with step 810. However, if the task has not completed, an error processing procedure is performed at block 812.
[00157] In block 810, the vehicle electronics 46 send the results to the central data processing system 10.
[00158] After step 812, the method continues with step 813. At step 813, the vehicle electronics 46, the data processing system 10, or both determine whether the error processing procedure has resolved the problem. If the error processing procedure has resolved the problem, the method continues with block 810. However, if the error processing procedure has not resolved the problem, the method continues with block 814.
[00159] In block 814, the vehicle electronics 46 send error information to the central data processing system 10 for analysis.
[00160] In block 815, which can follow block 810 or block 814, the process of FIG. 8A ends.
[00161] The process of FIG. 8B refers to detecting and managing messages or software corruption tasks in the vehicle electronics 46. The process of FIG. 8B begins at step 818. The process of FIG. 8B provides an illustrative example of step 803 in FIG. 8A, for example. Like reference numbers in FIG. 8A and FIG. 8B indicate like elements.
[00162] Prior to performing step 818, the data processor 71 or vehicle electronics 46 performs or performs a particular task. For example, data processor 71 may perform or perform the particular task in block 808 of FIG. 8A. A task refers to any process, discrete, identifiable procedures, or series of processes and procedures that are applied to input data, output data, intermediate data derived from the input data, or a precursor to the output data by the processor. 71. In one example, a task may include trigger-based logging of performance or diagnostic data associated with a controller 73 or an engine controller 74. In another example, a task comprises logging data into the vehicle electronics 46 to support engineering analysis or diagnostics on vehicle components, systems or performance.
[00163] In step 818, the resource monitor 74, corruption task module 65 or the data processor 71 determines whether the consumption of resources of the data processor (e.g., vehicle data processor 71) for a respective task exceeds a resource consumption threshold value. The resource consumption threshold value can be related to one or more of the following: (1) a measure of the processing output of the data processor 71 (for example, in total processing time duration, or in Megabytes or Gigabytes processed per second in total processing time duration) consumed to perform a corresponding particular task, (2) measuring the processing capacity of data processor 71 (for example, in total processing time duration, or in Megabytes or Gigabytes processed per second in the total duration of processing time) consumed to perform a particular corresponding task, and (3) measuring the percentage of total processing power consumed to perform a particular corresponding task, where the resource consumption threshold value indicates a historical consumption greater than the average or historical consumption greater than the median of the processing output of the data processor 71 or the processing capability of the data processor 71 for a corresponding task or a substantially similar task.
[00164] The resource monitor 74 is capable of estimating the data processing resource consumption for each respective task performed by the data processor 71 or the consumption percentage of the total processing capacity for each respective task. A task refers to any process, discrete, identifiable procedure, procedures or series of processes and procedures that are applied to input data, output data, intermediate data derived from the input data, or a precursor to the output data by data processor 71. For example, a task may include trigger-based logging of performance or diagnostics data associated with a controller 73 or a motor controller 74.
[00165] If the data processor resource consumption for a respective task exceeds a resource consumption threshold value, the method continues with step 824.
[00166] However, if the data processor resource consumption for a respective task is equal to or does not exceed the resource consumption threshold value, the method continues with step 820.
[00167] In step 820, while executing or attempting to execute a respective particular task, the alert 73 timer determines whether the value of the alert 73 timer expires without being reset during an interrupt interval. Alert timer 73 can monitor the performance of a particular task or group of tasks that must normally be performed or processed during the outage interval. If the time of alert timer 73 expires without being reset during the outage interval (eg, alert outage period), the method continues with step 824, where reset logic 73 can reset or reset the data processor 71, as previously described in block 826. However, if the alert timer 73 does not expire without being reset during the interruption interval (eg, alert interruption period), the method continues with step 822.
[00168] In step 822, the data processor 71 reads the next task in the queue for execution. The task can be arranged as a series of machine-level instructions in a data stack or in data registers associated with the data processor 71, its arithmetic logic unit, electronic data store, or another component with data that are readable by the data processor 71. After step 822, the method returns or continues with step 818. At 822, the data processor 71 may optionally wait an interval of time before returning to step 818, or delay such execution of according to interrupt procedures coordinated by the data processor 71.
[00169] In step 824, which may follow step 820, data processor 71 or cycle counter 75 increments cycle counter 75 in the data storage device for the corresponding particular task. Step 824 can be performed according to various techniques, which can be applied alternatively or cumulatively. According to a first technique, the cycle counter 75 in a vehicle data storage device 56 is incremented if the resource consumption (in block 818) exceeds the threshold value. According to a second technique, the cycle counter 75 in the vehicle data storage device 56 is incremented if the warning timer time expires 72 without being reset during the interruption period or interruption interval.
[00170] According to a third technique, a single 75-cycle counter can be allocated or assigned to each corresponding particular task for tracking purposes. The cycle counter value for each corresponding particular task is stored in vehicle data storage device 56 (e.g., cycle counter 75) in a manner that allows the cycle counter value to be preserved or retained when the data processor 71 is reset or reset. For example, vehicle data storage device 56 may comprise non-volatile electronic random access memory, an optical storage device, a magnetic storage device, or a magnetic disk drive that retains cycle counter values or other data. in the counter of cycle 75 when the data processor 71 is turned off, reset or reset.
[00171] At step 826, reset logic 73, alert timer 72 or corruption task module 65 resets or resets data processor 71. Data processor 71 or vehicle electronics 46 may be reset or reset in one or more of the following circumstances: (1) the data processor 71 is reset or reset if the alert timer time expires without being reset during the interrupt period or interrupt interval, or (2) the data processor 71 is reset or reset if the resource consumption for the respective particular task exceeds the threshold value. For example, in the case where alert timer 72 expires without reset or reset, a trigger value stored in a data log during the alert interruption period, alert timer 71 and reset logic 73 generate a reset or reset signal to data processor 71 to reset or reset data processor 71.
[00172] Step 828 follows step 826. In step 826, data processor 71, corruption task module 65, or cycle counter 75 determines whether data processor 71 is reset or reset more than a maximum number of times (e.g., three times or according to the technician-defined setting of the maximum number of times), indicated by reading a counter of cycle 75 in the data storage device 56. If the data processor 71 is reset or reset more than a maximum number of times (eg, three times or as per the technician-defined setting of the maximum number of times), the method continues with block 832. However, if data processor 71 is not reset or reinstated a maximum number of times, the method continues with block 830.
[00173] At block 830, data processor 71 may execute the cycle associated with the task again or may reschedule the task for execution by data processor 71, before returning to step 818. For example, data processor 71 or vehicle electronics 46 performs the particular task again after resetting or resetting data processor 71, if data processor 71 or vehicle electronics 46 has not been reset or reset more than a maximum number of times (e.g. , defined by a technician).
[00174] At block 832, data processor 71 or corruption task module 65 identifies or designates the task as a corruption message and flags task for not executing by data processor 71. The particular task is designated as a message of corruption by data processor 71 or corruption task module 65 if data processor 71 has been reset or reset a maximum number of times, indicated by cycle counter 75. Block 832 can be executed in accordance with various techniques which can be applied cumulatively or separately. According to a first technique, the data processor 71 or corruption task module 65 can segregate or isolate the corruption message in the data stored in a section of the data storage device 56 that is prohibited from read access or access. recording by one or more executable programs, or the corruption task module 65 or the data processor segregates or isolates the corruption message on the data storage device 56 (e.g. according to a security algorithm or operating system) to prevent reading or writing to one or more application programs.
[00175] According to a second technique, the data processor 71 or corruption task module 65 may prefer to delete the files or data records or file fragments associated with the corruption message or corruption task, either after segregation for the same period of time as in place of segregation.
[00176] According to a third technique, the data processor 71 is relieved from processing corrupted data messages that consume higher levels of target processing resources to improve processing efficiency and output. The data processor 71 can better perform other critical tasks in real time, where such critical tasks may comprise one or more of the following: high fidelity data collection or processing; collecting or processing diagnostic data; reprogramming one or more controllers (73, 74), or vehicle electronics 46; reconfiguration or recalibration of one or more controllers (73, 74), or vehicle electronics 46; control of internal combustion engine settings for economy or power; control of fuel metering adjustments; pollution control and emission controls; determination of vehicle location; determination of vehicle position, pitch, roll and yaw; vehicle navigation; vehicle protection; obstacle detection; obstacle avoidance; steering, braking or controlling the vehicle to avoid colliding with obstacles or hitting obstacles; and detecting, sensing or scanning detecting an area or environment around the vehicle with visual, audio, infrared, laser, near infrared, stereo vision or other devices.
[00177] According to a fourth technique, the data processor 71 or the corruption task module 65 saves or stores the fact that it performed a particular task, but did not complete the particular task for the corruption task module 65 or the data storage device 56. The corrupt task module 65 may contain a task processing queue to ensure that the identity of the corrupt tasks has not been lost in power cycles, reset or reset of the data processor 71 or the vehicle electronics 46. The data processor 71 or the corruption task module 65 reads a particular task from the task processing queue at the beginning and before running the particular task to determine whether or not the task qualifies as a corruption task or contains a corruption message. If the corruption task module 65 indicates that a task is a corrupt task, the data processor 71 will not run the task and the data processor 71 will send back a corruption task state to the central electronic data processing system. 10 (e.g., corrupted status message for display on a network dashboard), the user interface 41 of the first service technician terminal 40, or the user interface 41 of the second service technician terminal 42 via the communication network 36. The status of the corruption task will inform the service technician that the particular task has not been performed, that the software has not been installed on the vehicle electronics 46 or on the controllers (73, 74), a process of calibration of the vehicle electronics 46 could not be performed, or that a diagnostic process could not be performed due to a corruption message in the software.
[00178] The method of FIG. 9 refers to processing or importing engineering data into the diagnostic system. The method starts at block 901.
[00179] In block 901, engineering data is created.
[00180] In block 902, the created engineering data is loaded or fed into the central data processing system 10. For example, a user enters the engineering data created in the central data processing system 10 through a user interface. user 41 associated with a first service technician terminal 40, a second service technician terminal 42, or another terminal.
[00181] In block 903, the central data processing system 10 imports the engineering data into an authorization system.
[00182] In block 904, the central data processing system 10 incorporates additional terminology, instructions or other supplementary data to the engineering data imported through the authorization system. The supplementary data supports the service center computer application 301, which can be displayed by a user on the user interface 41 of a terminal.
[00183] In block 905, the central data processing system 10 loads the engineering data and supplementary data into the service center computer application 301.
[00184] In block 906, the method of FIG. 9 ends.
[00185] FIG. 10 provides an illustrative example of a billing system. The billing system may be implemented by remote data processor 12 as software instructions in central data processing system 10. Software instructions may be stored in remote data storage device 14, for example.
[00186] The billing system comprises a revenue module 950 and a cost of sales module 972 that provide input data to the 957 calculator. The 957 calculator in turn provides data to an accounting transfer module 959. Accounting Transfer System 959 communicates with one or more accounting systems (eg, first accounting system 960 and second accounting system 961). The first accounting system 960 can serve a group of traders (eg, first trader 962, second trader 963, third trader 964, fourth trader 965, and up to an Nth trader 966, where N is an integer greater than or equal to to five in this example). A second accounting system 961 can serve one or more distributors (970, 967) and a service center 968.
[00187] The recipe module 950 further comprises a vehicle service component 951, a communication service component 952, and remote management database 953. The remote management database 953 stores transaction records and other information of collection.
[00188] The 972 cost of sales module comprises a telecom provider cost estimator 955, an information technique cost estimator 954, and a total cost of sales estimator 956. The information technique cost estimator 954 estimates the maintenance and operation costs of the central data processing system 10, one or more servers, and other hardware and infrastructure.
[00189] Having described the preferred embodiment, it will be apparent that various modifications can be made without departing from the scope of the invention defined in the appended claims.

权利要求:
Claims (11)
[0001]
1. Method of performing remote diagnostics in a vehicle, the method comprising: collecting and storing high fidelity data from measured events in a buffer memory or a data storage device (56) by means of a controller (73, 74) of the vehicle electronic components (46) that are associated with sensors or measurement devices in the vehicle, the storage and accumulation of high-fidelity data made for further transmission via a vehicle data bus (72) for subsequent analysis in a system central data processing (10) consistent with configuration files (30) to support engineering analysis or diagnostics on vehicle components, systems or performance; retrieving supplemental data via a low-bandwidth transmission at a lower sampling rate than the sampling rate of the hi-fi data from the electronic components (46) in the vehicle to supplement the recorded hi-fi data; transmitting the recorded hi-fi data and retrieved supplementary data to the central electronic data processing system (10) and processing, with the central electronic data processing system (10), the recorded hi-fi data and retrieved supplementary data to generate a diagnostic status report message; organizing the diagnostic reporting message, the recorded high-fidelity data, and the retrieved supplemental data into a data marketplace or diagnostic database (28) to support engineering analysis or diagnostics on components, systems, or vehicle performance; characterized by the fact that high-fidelity data comprises data gathered at a sample rate greater than the sample rates required by the controller (73, 74) to perform non-diagnostic functions during normal controller operation (73, 74).
[0002]
2. Method according to claim 1, characterized in that the low-bandwidth transmission comprises a wireless transmission between electronic components of the vehicle (46) and the central electronic data processing system (10) or a another remote data processing system, where bandwidth is limited to meet or exceed a certain minimum threshold of reliability or signal quality or comply with a bandwidth limitation provided by a satellite or other service provider without thread.
[0003]
3. Method according to claim 1, characterized in that the organization comprises identifying trends in the diagnostic database (28).
[0004]
4. Method according to claim 1, characterized in that it further comprises: determining status or progress of diagnostic requests; and displaying the determined status to a user at a user terminal (40, 42) in communication with the central electronic data processing system (10).
[0005]
5. Method according to claim 1, characterized in that it further comprises: displaying real-time data readings from the vehicle to a user at a user terminal (40.42) in communication with the data processing system central electronic (10).
[0006]
6. Method according to claim 1, characterized in that it comprises: supporting customer selection of a service center to remotely perform service in a vehicle through selectable settings via network address.
[0007]
7. Method according to claim 1, characterized in that it further comprises: performing tests on the vehicle through a remote terminal (40, 42) in communication with at least one of the electronic components of the vehicle (46) and the system central electronic data processing system (10).
[0008]
8. Method according to claim 1, characterized in that it additionally comprises: user-based billing system for diagnostic and remote programming sessions.
[0009]
9. Method according to claim 1, characterized in that the high-fidelity data is collected through a data collector in an engine controller (74) and in that the high-fidelity data comprises data related to events injection or fuel metering system events.
[0010]
10. Method according to claim 1 characterized in that the recovery of supplementary data through low bandwidth transmission is performed in real time through the vehicle data bus (72).
[0011]
11. A system for performing remote diagnostics on a vehicle, the system comprising: electronic components of the vehicle (46) comprising a controller (73, 74) adapted to collect and store high fidelity data from measured events in a buffer memory or a device of data storage (56), the controller (73, 74) associated with sensors or measurement devices in the vehicle and adapted to store and accumulate the high fidelity data for further transmission via a vehicle data bus (72) , for subsequent analysis in a central data processing system (10) consistent with configuration files (30) to support engineering analysis or diagnostics on components, systems or vehicle performance; a retriever (62) for retrieving supplemental data via a low-bandwidth transmission at a lower sampling rate than the sampling rate of the high-fidelity data from the electronics (46) in the vehicle to supplement the high-end data. registered loyalty; wherein the vehicle electronics (46) are configured to transmit the recorded high fidelity data and retrieved supplemental data to the central electronic data processing system (10), wherein the central electronic data processing system (10) is configured to generate a diagnostic status report message by processing the recorded high-fidelity data and retrieved supplemental data; the central electronic data processing system is adapted to organize the diagnostic report message, the recorded high-fidelity data and the retrieved supplementary data into a data market or diagnostic database (28) to support analysis or diagnostics of engineering in vehicle components, systems or performance; characterized by the fact that high-fidelity data comprises data gathered at a sample rate greater than the sample rates required by the controller (73, 74) to perform non-diagnostic functions during normal controller operation (73, 74).

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112013003141B1|2021-05-25|method and system for performing remote diagnostics in a vehicle

---

CA2472854C|2008-09-09|Distributed expert diagnostic service and system

---

CA2709594C|2019-06-11|Gen ii meter system with multiple processors, multiple detection sensor types, fault tolerance methods, power sharing and multiple user interface methods

---

US20160071338A1|2016-03-10|Diagnostic unit and method

---

US9659417B2|2017-05-23|Systems and methods for extraction and telemetry of vehicle operational data from an internal automotive network

---

US20040138790A1|2004-07-15|Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components

---

US20050060070A1|2005-03-17|Wireless communication framework

---

CN201674532U|2010-12-15|Remote updating system of vehicle information acquisition device

---

CN103080719B|2016-04-06|For the method and system of the diagnosis or software maintenance that perform vehicle

---

AU2022200298A1|2022-02-10|GEN II meter system with multiple processors, multiple detection sensor types, fault tolerance methods, power sharing and multiple user interface methods

---

US20140058762A1|2014-02-27|Methods and systems for consumer controlled insurance data management

---

CN110928561A|2020-03-27|Vehicle controller software version management method and device, vehicle and storage medium

---

KR20200051517A|2020-05-13|Fluid management controller

---

CN110908955A|2020-03-24|Management system of IO device description file

---

KR200404173Y1|2005-12-19|auto gater for automatic meter reading system

同族专利:

---

公开号 | 公开日

---

CN103080720B|2016-06-15|

---

BR112013003141A2|2020-06-30|

---

EP2699883A1|2014-02-26|

---

WO2012021905A8|2013-04-11|

---

EP2603784A4|2016-12-28|

---

BR112013003140B1|2020-10-27|

---

EP2699883B1|2020-09-16|

---

US20120041638A1|2012-02-16|

---

WO2012021905A1|2012-02-16|

---

AU2011289164A1|2013-03-14|

---

AU2011289162A1|2013-02-28|

---

BR112013003140B8|2021-05-04|

---

US8751100B2|2014-06-10|

---

WO2012021903A1|2012-02-16|

---

EP2603784B1|2021-04-28|

---

CN103154694B|2016-03-30|

---

BR112013003140A2|2016-06-28|

---

AU2011289164B2|2015-07-23|

---

BR112013003139A2|2016-06-28|

---

EP2603784A1|2013-06-19|

---

BR112013003139B1|2020-04-07|

---

EP2699883A4|2016-12-14|

---

US9043078B2|2015-05-26|

---

US20120041635A1|2012-02-16|

---

ES2879869T3|2021-11-23|

---

AU2011289163A1|2013-02-28|

---

EP2614348A4|2017-01-11|

---

CN103154694A|2013-06-12|

---

WO2012021904A1|2012-02-16|

---

US20120041636A1|2012-02-16|

---

EP2614348A1|2013-07-17|

---

US8412406B2|2013-04-02|

---

AU2011289163B2|2015-06-11|

---

CN103080720A|2013-05-01|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

IL50822A|1975-12-11|1979-09-30|Hughes Aircraft Co|Signal sampling system|

---

GB1601811A|1977-02-22|1981-11-04|Morling R C S|Signal processing|

---

US5175537A|1990-03-29|1992-12-29|Micro Technology, Inc.|Method and apparatus for scheduling access to a CSMA communication medium|

---

EP0521892A1|1990-03-29|1993-01-13|Micro Technology, Inc.|Method and apparatus for scheduling access to a csma communication medium|

---

JP2758742B2|1991-07-19|1998-05-28|日本電気株式会社|Malfunction detection method|

---

US5388841A|1992-01-30|1995-02-14|A/N Inc.|External memory system having programmable graphics processor for use in a video game system or the like|

---

US5541840A|1993-06-25|1996-07-30|Chrysler Corporation|Hand held automotive diagnostic service tool|

---

JP3331036B2|1994-01-13|2002-10-07|株式会社日立国際電気|Flight data recorder|

---

US8140358B1|1996-01-29|2012-03-20|Progressive Casualty Insurance Company|Vehicle monitoring system|

---

US5908455A|1996-10-07|1999-06-01|Hewlett-Packard Company|High performance automotive diagnostics instrumentation architecture|

---

US6904110B2|1997-07-31|2005-06-07|Francois Trans|Channel equalization system and method|

---

DE19921845A1|1999-05-11|2000-11-23|Bosch Gmbh Robert|Diagnostic test device for motor vehicles with programmable control units|

---

US6434458B1|1999-10-28|2002-08-13|General Electric Company|Method and apparatus for vehicle data transfer optimization|

---

DE10037397A1|2000-08-01|2002-02-14|Daimler Chrysler Ag|Software loading method|

---

US20050060070A1|2000-08-18|2005-03-17|Nnt, Inc.|Wireless communication framework|

---

US7092803B2|2000-08-18|2006-08-15|Idsc Holdings, Llc|Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components|

---

US20050065678A1|2000-08-18|2005-03-24|Snap-On Technologies, Inc.|Enterprise resource planning system with integrated vehicle diagnostic and information system|

---

JP3834463B2|2000-10-13|2006-10-18|株式会社日立製作所|In-vehicle failure alarm reporting system|

---

US7149206B2|2001-02-08|2006-12-12|Electronic Data Systems Corporation|System and method for managing wireless vehicular communications|

---

US6611740B2|2001-03-14|2003-08-26|Networkcar|Internet-based vehicle-diagnostic system|

---

US20020130691A1|2001-03-15|2002-09-19|Silvestri Paul A.|Method and apparatus for fast lock of delay lock loop|

---

US7505467B1|2001-03-30|2009-03-17|Cisco Technology, Inc.|Method and apparatus for dynamic bandwidth management for voice traffic in a digital communications network|

---

DE10133945A1|2001-07-17|2003-02-06|Bosch Gmbh Robert|Method and device for exchanging and processing data|

---

WO2003015002A1|2001-08-10|2003-02-20|Tellsyn Co., Ltd|System and method for collecting vehicle data and diagnosing the vehicle, and method for automatically setting the vehicle convenience apparatus using smartcard|

---

US6609051B2|2001-09-10|2003-08-19|Daimlerchrysler Ag|Method and system for condition monitoring of vehicles|

---

DE10157188A1|2001-11-22|2003-05-28|G I N Mbh|Programmable data logger and classifier for CAN systems|

---

AU2003215142A1|2002-02-05|2003-09-02|Cleaire Advanced Emission Controls|Apparatus and method for simultaneous monitoring, logging, and controlling of an industrial process|

---

US6691007B2|2002-04-04|2004-02-10|The Boeing Company|Vehicle condition monitoring system|

---

US6993681B2|2002-04-15|2006-01-31|General Electric Corporation|Remote administration in a distributed system|

---

US6745151B2|2002-05-16|2004-06-01|Ford Global Technologies, Llc|Remote diagnostics and prognostics methods for complex systems|

---

US6931309B2|2003-05-06|2005-08-16|Innosurance, Inc.|Motor vehicle operating data collection and analysis|

---

JP4223909B2|2003-09-24|2009-02-12|三菱電機株式会社|In-vehicle electronic control unit|

---

DE10360125A1|2003-12-20|2005-07-21|Daimlerchrysler Ag|Data loggin in a motor vehicle|

---

US7111185B2|2003-12-23|2006-09-19|Micron Technology, Inc.|Synchronization device with delay line control circuit to control amount of delay added to input signal and tuning elements to receive signal form delay circuit|

---

JP4509602B2|2004-02-27|2010-07-21|富士重工業株式会社|Operator side system and mode file identification method|

---

US7506309B2|2004-03-23|2009-03-17|General Motors Corporation|Method for managing vehicle software configuration updates|

---

CN100509499C|2004-05-28|2009-07-08|深圳市英唐智能控制股份有限公司|Wireless monitoring and fault diagnostic system and method for vehicle|

---

US20060101311A1|2004-10-25|2006-05-11|Spx Corporation|Connectivity between a scan tool and a remote device and method|

---

US7239946B2|2004-10-25|2007-07-03|General Motors Corporation|Vehicles fault diagnostic systems and methods|

---

US7272475B2|2004-12-02|2007-09-18|General Motors Corporation|Method for updating vehicle diagnostics software|

---

US7161391B2|2004-12-03|2007-01-09|Micron Technology|Skew tolerant high-speed digital phase detector|

---

JP4060322B2|2005-03-28|2008-03-12|三菱電機株式会社|Application management apparatus and storage medium storing software thereof|

---

US20060229777A1|2005-04-12|2006-10-12|Hudson Michael D|System and methods of performing real-time on-board automotive telemetry analysis and reporting|

---

US7346728B1|2005-04-18|2008-03-18|Intel Corporation|Method and apparatus for a hub capable of being self-powered for use in a USB-compliant system|

---

JP2006338605A|2005-06-06|2006-12-14|Denso Corp|Program failure monitoring method and program failure monitoring device|

---

US7882394B2|2005-07-11|2011-02-01|Brooks Automation, Inc.|Intelligent condition-monitoring and fault diagnostic system for predictive maintenance|

---

US7920944B2|2005-10-21|2011-04-05|General Motors Llc|Vehicle diagnostic test and reporting method|

---

US7774130B2|2005-12-07|2010-08-10|Gary Thomas Pepper|Methods and system for determining consumption and fuel efficiency in vehicles|

---

US20070152503A1|2005-12-30|2007-07-05|Kowalick Thomas M|Vehicle connector lockout apparatus and method of using same|

---

DE102006009098A1|2006-02-28|2007-08-30|Daimlerchrysler Ag|Diagnosis data transmitting method for e.g. passenger car, involves transmitting connection request via channel of radio interface to onboard communication module found in vehicle|

---

US7631229B2|2006-04-24|2009-12-08|Freescale Semiconductor, Inc.|Selective bit error detection at a bus device|

---

JP5028852B2|2006-04-25|2012-09-19|株式会社デンソー|Vehicle communication system|

---

JP4187028B2|2006-09-13|2008-11-26|ヤマハ株式会社|Network system and acoustic signal processing apparatus|

---

US7519933B2|2006-09-21|2009-04-14|Sun Microsystems, Inc.|Converging repeater methodology for channel-limited SOC microprocessors|

---

US20090254243A1|2006-09-28|2009-10-08|Fujitsu Ten Limited|On-board machine, frequency collecting device, and frequency collecting method|

---

US8213321B2|2007-02-01|2012-07-03|Deere & Company|Controller area network condition monitoring and bus health on in-vehicle communications networks|

---

US20080291014A1|2007-05-23|2008-11-27|Toyota Engineering & Manufacturing North America, Inc.|System and method for remote diagnosis and repair of a plant malfunction with software agents|

---

US8200376B2|2007-07-30|2012-06-12|Symvionics, Inc.|Vehicle performance monitoring system with multi-level caching|

---

US8185609B2|2007-11-27|2012-05-22|The Boeing Company|Method and apparatus for processing commands in an aircraft network|

---

GB2457279A|2008-02-08|2009-08-12|Airmax Group Plc|Configuration of an electronic control system for controlling the operation of at least one component of a vehicle|

---

JP2009286295A|2008-05-30|2009-12-10|Hitachi Ltd|On-vehicle information-collecting system and data collecting method in on-vehicle information-collecting device|

---

US8700255B2|2008-10-08|2014-04-15|Trimble Navigation Limited|Devices, systems, and methods for monitoring driver and vehicle behavior|

---

US8548669B2|2009-01-08|2013-10-01|New Flyer Industries Canada Ulc|System and method for monitoring operation of vehicles|

---

US8352115B2|2009-06-30|2013-01-08|GM Global Technology Operations LLC|Methods and apparatus for initiating service sessions between vehicles and service providers|

---

US9367967B2|2009-09-29|2016-06-14|GM Global Technology Operations LLC|Systems and methods for odometer monitoring|

---

CN201548405U|2009-11-13|2010-08-11|上汽通用五菱汽车股份有限公司|Computer-type vehicle fault diagnosis device|

---

US20110130916A1|2009-12-01|2011-06-02|Ise Corporation|Location Based Vehicle Data Logging and Diagnostic System and Method|

---

US8392698B2|2010-04-16|2013-03-05|Cisco Technology, Inc.|System and method for providing prefixes indicative of mobility properties in a network environment|

---

US20120008460A1|2010-07-12|2012-01-12|Wireless Seismic|Data acquisition system with removable|

---

US8751100B2|2010-08-13|2014-06-10|Deere & Company|Method for performing diagnostics or software maintenance for a vehicle|US10056008B1|2006-06-20|2018-08-21|Zonar Systems, Inc.|Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use|

---

US20120253551A1|2009-01-30|2012-10-04|Sammy Halimi|Systems and Methods for Providing Telematic Services to Vehicles|

---

US8626152B2|2008-01-31|2014-01-07|Agero Connected Sevices, Inc.|Flexible telematics system and method for providing telematics to a vehicle|

---

US8934866B2|2009-04-20|2015-01-13|Aetherpal Inc.|System to assist a mobile device subscriber to perform self-diagnosis of the mobile device|

---

US8868679B2|2010-05-24|2014-10-21|Nuance Communications, Inc.|Systems, methods and articles for providing communications and services via a peer-to-peer network over a data transport link|

---

JP6034782B2|2010-05-25|2016-11-30|ザ・リージェンツ・オブ・ザ・ユニバーシティー・オブ・カリフォルニアＴｈｅ Ｒｅｇｅｎｔｓ Ｏｆ Ｔｈｅ Ｕｎｉｖｅｒｓｉｔｙ Ｏｆ Ｃａｌｉｆｏｒｎｉａ|BAMBAM: Simultaneous comparative analysis of high-throughput sequencing data|

---

US9646134B2|2010-05-25|2017-05-09|The Regents Of The University Of California|Bambam: parallel comparative analysis of high-throughput sequencing data|

---

US8751100B2|2010-08-13|2014-06-10|Deere & Company|Method for performing diagnostics or software maintenance for a vehicle|

---

WO2012043167A1|2010-09-27|2012-04-05|日本電気株式会社|Information processing system, method for checking vehicle, and program for checking vehicle|

---

US20160203655A1|2011-01-18|2016-07-14|Control-Tec, Llc|Multiple-Mode Data Acquisition System|

---

US8626904B1|2011-03-09|2014-01-07|Symantec Corporation|Detecting and reporting livelocks in a computer|

---

DE102011076638A1|2011-05-27|2012-11-29|Stephan Kaufmann|A method of vehicle communication via a vehicle-implemented vehicle diagnostic system, interface module and vehicle diagnostic interface and diagnostic and control network for a plurality of vehicles|

---

US8996235B2|2011-11-14|2015-03-31|GM Global Technology Operations LLC|Repair assist system for vehicle servicing|

---

US9181878B2|2011-12-19|2015-11-10|Honeywell International Inc.|Operations support systems and methods for calculating and evaluating engine emissions|

---

US8880277B2|2012-02-29|2014-11-04|GM Global Technology Operations LLC|Methods and systems for diagnosing a vehicle|

---

US20130261939A1|2012-04-01|2013-10-03|Zonar Systems, Inc.|Method and apparatus for matching vehicle ecu programming to current vehicle operating conditions|

---

CN104503861A|2012-04-20|2015-04-08|华为技术有限公司|Abnormality handling method and system, agency device and control device|

---

US20130311074A1|2012-05-17|2013-11-21|Webtech Wireless Inc.|Ignition event generation using data from vehicle bus|

---

FR2992079A1|2012-06-15|2013-12-20|France Telecom|DEVICE AND METHOD FOR EXTRACTING DATA ON A COMMUNICATION BUS OF A MOTOR VEHICLE|

---

GB2503459A|2012-06-26|2014-01-01|Nordic Semiconductor Asa|Multiple hardware registers for watchdog timer preventing erroneous microprocessor system reset|

---

US9329917B2|2012-06-28|2016-05-03|Arnott, Inc.|Vehicle suspension augmentation devices, systems and methods|

---

US8527139B1|2012-08-28|2013-09-03|GM Global Technology Operations LLC|Security systems and methods with random and multiple change-response testing|

---

US9090265B2|2012-08-28|2015-07-28|GM Global Technology Operations LLC|Active safety systems of vehicles with graphical microprocessors|

---

US8831585B2|2012-08-31|2014-09-09|Nuance Communications, Inc.|Systems, methods and articles for a communications device providing communications and services involving automobile head units|

---

US8799360B2|2012-08-31|2014-08-05|Tweedle Group, Inc.|Systems, methods and articles for a server providing communications and services involving automobile head units|

---

DE102012017451A1|2012-09-04|2014-03-06|Claas Agrosystems Kgaa Mbh & Co. Kg|telemetry device|

---

US9510067B2|2012-10-18|2016-11-29|GM Global Technology Operations LLC|Self-diagnostic non-bussed control module|

---

KR101438978B1|2012-12-31|2014-09-11|현대자동차주식회사|Method and system for reprogramming|

---

GB2510384B|2013-02-01|2017-11-29|Jaguar Land Rover Ltd|Vehicle diagnostics apparatus and method|

---

US20140309905A1|2013-04-05|2014-10-16|Michael Drew|System and method for sending and receiving messages between an electronic control unit of a vehicle and an external device|

---

GB2519704B|2013-04-26|2017-01-04|Jaguar Land Rover Ltd|Vehicle diagnostics methods and apparatus|

---

US9402174B2|2013-05-06|2016-07-26|Verizon Telematics Inc.|Vehicle driver identification using portable device|

---

US9379855B2|2013-06-03|2016-06-28|MiCOM Labs, Inc.|Method and apparatus for a remote modular test system|

---

US9286152B2|2013-06-14|2016-03-15|Microsoft Technology Licensing, Llc|Securely obtaining memory content after device malfunction|

---

DE102013218075A1|2013-07-04|2015-01-08|Robert Bosch Gmbh|Device and measuring method for determining the internal delay time of a CAN bus connection unit|

---

KR101491293B1|2013-08-09|2015-02-10|현대자동차주식회사|Gateway apparatus and message routing method thereof|

---

FI126436B|2013-08-23|2016-11-30|Konecranes Global Oy|User rights management in connection with a crane|

---

US9092020B2|2013-10-08|2015-07-28|GM Global Technology Operations LLC|Calibration data selection|

---

CN103577233A|2013-11-07|2014-02-12|深圳市元征科技股份有限公司|OBDII code reading card device and system and method for upgrading same|

---

CN104699686A|2013-12-04|2015-06-10|广州汽车集团股份有限公司|Vehicle-mounted control module and matching method thereof|

---

KR101720440B1|2013-12-11|2017-03-27|가부시키가이샤 고마쓰 세이사쿠쇼|Work machine, management system and management method|

---

AU2014377573B2|2014-01-17|2020-03-12|Kohler Co.|Fleet management system|

---

US9878631B2|2014-02-25|2018-01-30|Elwha Llc|System and method for predictive control of an energy storage system for a vehicle|

---

US9056556B1|2014-02-25|2015-06-16|Elwha Llc|System and method for configuration and management of an energy storage system for a vehicle|

---

US9079505B1|2014-02-25|2015-07-14|Elwah LLC|System and method for management of a fleet of vehicles having an energy storage system|

---

US20160012401A1|2014-07-08|2016-01-14|Navico Holding As|Methods for Discovering and Purchasing Content for Marine Electronics Device|

---

DE102014213503A1|2014-07-11|2016-01-14|Bayerische Motoren Werke Aktiengesellschaft|Method for monitoring software in a road vehicle|

---

DE102014213922B4|2014-07-17|2020-02-20|Continental Automotive Gmbh|Vehicle infotainment system|

---

CN104181839A|2014-08-07|2014-12-03|深圳市元征科技股份有限公司|Method and device for processing real-time traveling data of vehicles|

---

US9401053B2|2014-09-09|2016-07-26|GM Global Technology Operations LLC|Fault notifications for vehicles|

---

DE102014113371A1|2014-09-17|2016-03-17|Knorr-Bremse Systeme für Schienenfahrzeuge GmbH|Method for monitoring and diagnosing components of a rail vehicle, with expandable evaluation software|

---

US9373203B1|2014-09-23|2016-06-21|State Farm Mutual Automobile Insurance Company|Real-time driver monitoring and feedback reporting system|

---

US9056616B1|2014-09-23|2015-06-16|State Farm Mutual Automobile Insurance|Student driver feedback system allowing entry of tagged events by instructors during driving tests|

---

CN107000687B|2014-09-29|2019-09-13|莱尔德无线技术（上海）有限公司|Remote information process device|

---

US9689336B2|2014-11-10|2017-06-27|Caterpillar Inc.|Engine system utilizing modal weighted engine optimization|

---

US20160131069A1|2014-11-10|2016-05-12|Caterpillar Inc.|Engine system utilizing cloud based engine optimization|

---

US20160131062A1|2014-11-10|2016-05-12|Caterpillar Inc.|Engine system utilizing selective engine optimization|

---

US9773354B2|2014-12-11|2017-09-26|Hyundai Motor Company|Terminal mounted in vehicle, control method thereof, data center and control method thereof|

---

CN105758648B|2014-12-19|2018-08-28|北京宝沃汽车有限公司|The test method and device of vehicle performance|

---

FR3034910B1|2015-04-10|2018-04-27|Psa Automobiles Sa.|METHOD FOR ACHIEVING REMOTE ACTIONS IN COMMUNICATION ELECTRONIC EQUIPMENT OF VEHICLES, AND ASSOCIATED COMMUNICATION DEVICE|

---

US10373523B1|2015-04-29|2019-08-06|State Farm Mutual Automobile Insurance Company|Driver organization and management for driver's education|

---

US9586591B1|2015-05-04|2017-03-07|State Farm Mutual Automobile Insurance Company|Real-time driver observation and progress monitoring|

---

CN106293979B|2015-06-25|2019-11-15|伊姆西公司|Method and apparatus of the detection procedure without response|

---

US10118592B2|2015-08-04|2018-11-06|Ford Global Technologies, Llc|Diagnostic port protection to body control module|

---

US10093232B2|2015-09-16|2018-10-09|Truck-Lite Co., Llc|Telematics road ready system|

---

US10388161B2|2015-09-16|2019-08-20|Truck-Lite Co., Llc|Telematics road ready system with user interface|

---

JP6864006B2|2015-12-21|2021-04-21|バイエリシエ・モトーレンウエルケ・アクチエンゲゼルシヤフト|How to modify control equipment related to automobile safety and / or security and related equipment|

---

KR20170082770A|2016-01-07|2017-07-17|현대자동차주식회사|In the case of the ECU reprograming, secondary battery prevent deep discharging of the method and apparatus|

---

DE102016201162B4|2016-01-27|2018-10-18|Bayerische Motoren Werke Aktiengesellschaft|Transmitting a message to be displayed to a display device of a motor vehicle|

---

US9824512B2|2016-02-05|2017-11-21|Ford Global Technologies, Llc|Adjusting diagnostic tests based on collected vehicle data|

---

US10055199B2|2016-02-10|2018-08-21|NodeSource, Inc.|Transparent node runtime and management layer|

---

GB2548163A|2016-03-11|2017-09-13|V-Nova Ltd|Data processing devices, data processing units, methods and computer programs for processsing telemetry data|

---

CN109070745B|2016-03-25|2021-09-03|康明斯有限公司|System and method for adjusting vehicle operating parameters based on vehicle duty cycle|

---

US10325037B2|2016-04-28|2019-06-18|Caterpillar Inc.|System and method for analyzing operation of component of machine|

---

US10417839B2|2016-05-25|2019-09-17|Navigation Research Company|System and method for vehicle assessment and uses thereof|

---

JP6736980B2|2016-05-27|2020-08-05|オムロン株式会社|System and semiconductor device|

---

US10235631B2|2016-07-01|2019-03-19|Deere & Company|Methods and apparatus to predict machine failures|

---

US10950229B2|2016-08-26|2021-03-16|Harman International Industries, Incorporated|Configurable speech interface for vehicle infotainment systems|

---

US20180088959A1|2016-09-28|2018-03-29|Delphi Technologies, Inc.|Automated-vehicle resource management system|

---

US10353691B2|2016-09-30|2019-07-16|Cummins Inc.|Updating electronic controller through telematics|

---

US10634111B2|2016-12-12|2020-04-28|Kohler Co.|Ignition module for internal combustion engine with integrated communication device|

---

US10102693B1|2017-05-30|2018-10-16|Deere & Company|Predictive analysis system and method for analyzing and detecting machine sensor failures|

---

CN107248945A|2017-06-15|2017-10-13|北京全路通信信号研究设计院集团有限公司|A kind of MVB controller|

---

US10816354B2|2017-08-22|2020-10-27|Tusimple, Inc.|Verification module system and method for motion-based lane detection with multiple sensors|

---

US10565457B2|2017-08-23|2020-02-18|Tusimple, Inc.|Feature matching and correspondence refinement and 3D submap position refinement system and method for centimeter precision localization using camera-based submap and LiDAR-based global map|

---

US10762673B2|2017-08-23|2020-09-01|Tusimple, Inc.|3D submap reconstruction system and method for centimeter precision localization using camera-based submap and LiDAR-based global map|

---

US10217066B1|2017-08-28|2019-02-26|Deere & Company|Methods and apparatus to monitor work vehicles and to generate worklists to order the repair of such work vehicles should a machine failure be identified|

---

US10953881B2|2017-09-07|2021-03-23|Tusimple, Inc.|System and method for automated lane change control for autonomous vehicles|

---

US10953880B2|2017-09-07|2021-03-23|Tusimple, Inc.|System and method for automated lane change control for autonomous vehicles|

---

EP3738106A4|2018-01-11|2021-09-08|TuSimple, Inc.|Monitoring system for autonomous vehicle operation|

---

CN108282365A|2018-01-19|2018-07-13|北京新能源汽车股份有限公司|A kind of vehicle configuration method, device, terminal, car-mounted terminal and vehicle|

---

US11009356B2|2018-02-14|2021-05-18|Tusimple, Inc.|Lane marking localization and fusion|

---

US11009365B2|2018-02-14|2021-05-18|Tusimple, Inc.|Lane marking localization|

---

CN110378184A|2018-04-12|2019-10-25|北京图森未来科技有限公司|A kind of image processing method applied to automatic driving vehicle, device|

---

US20190354098A1|2018-05-21|2019-11-21|Deere & Company|Gateway interface for a work machine|

---

US20190378355A1|2018-06-12|2019-12-12|GM Global Technology Operations LLC|Remote vehicle electronics configuration|

---

US20200005555A1|2018-06-29|2020-01-02|K&N Engineering, Inc.|Vehicle Performance Wireless Interface|

---

US10845800B2|2018-10-08|2020-11-24|Ford Global Technologies, Llc|Vehicle software check|

---

US10942271B2|2018-10-30|2021-03-09|Tusimple, Inc.|Determining an angle between a tow vehicle and a trailer|

---

US11014534B2|2019-07-13|2021-05-25|Toyota Motor North America, Inc.|Remote access of transports|

---

US11233713B2|2019-07-19|2022-01-25|Deere & Company|Controller area network and connectivity health troubleshooting system|

---

US11217041B2|2019-07-29|2022-01-04|Toyota Motor North America, Inc.|Tracking of transport data|

---

CN110609835A|2019-08-19|2019-12-24|广州明珞汽车装备有限公司|Control method, system and storage medium for storing vehicle type position information|

---

CN110597229A|2019-09-24|2019-12-20|中国第一汽车股份有限公司|Vehicle diagnosis mutual exclusion method and device, vehicle and storage medium|

---

US11169795B2|2019-10-09|2021-11-09|Toyota Motor North America, Inc.|Management of transport software updates|

---

US20210107679A1|2019-10-10|2021-04-15|Ge Aviation Systems Limited|Integrated system for improved vehicle maintenance and safety|

法律状态:
2020-07-14| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2020-07-21| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2021-04-13| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2021-05-25| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 24/08/2011, OBSERVADAS AS CONDICOES LEGAIS. |

---

2021-12-07| B17A| Notification of administrative nullity (patentee has 60 days time to reply to this notification)|Free format text: REQUERENTE DA NULIDADE: MAQUINAS AGRICOLAS JACTO S/A. - 870210107181 - 19/11/2021 |

优先权:

---

申请号 | 申请日 | 专利标题

---

US37349310P| true| 2010-08-13|2010-08-13|

---

US61/373493|2010-08-13|

---

US61/373,493|2010-08-13|

---

US12/879176|2010-09-10|

---

US12/879,176|2010-09-10|

---

US12/879,176|US9043078B2|2010-08-13|2010-09-10|Method and system for performing diagnostics or software maintenance for a vehicle|

---

PCT/US2011/048929|WO2012021905A1|2010-08-13|2011-08-24|Method and system for performing diagnostics or software maintenance for a vehicle|

---